Skip to content

EOP rebrand (minor link and link title changes) #13341

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
chrisda wants to merge 1 commit into
base: master
Choose a base branch
from
Open

EOP rebrand (minor link and link title changes) #13341

chrisda wants to merge 1 commit into from

Conversation

@chrisda
Copy link

@chrisda chrisda commented Dec 19, 2025 •
edited
Loading

Change(s):
EOP rebranding updates in links only. Same link changes in all 4 'articles':

  • [Microsoft Defender for Office 365](https://www.microsoft.com/microsoft-365/security/office-365-defender) to [Microsoft Defender for Office 365](https://learn.microsoft.com/defender-office-365/mdo-about).
  • [Anti-Spam protection in Exchange Online Protection](https://docs.microsoft.com/microsoft-365/security/office-365-security/anti-spam-protection) to [Anti-spam protection in cloud organizations](https://learn.microsoft.com/defender-office-365/anti-spam-protection-about).
  • [Configure Anti-Spam Policies in Exchange Online Protection](https://docs.microsoft.com/microsoft-365/security/office-365-security/configure-your-spam-filter-policies) to [Configure anti-spam policies for cloud mailboxes](https://learn.microsoft.com/defender-office-365/anti-spam-policies-configure).

Reason for Change(s):

  • Marketing driven. Seek and destroy all references to "Exchange Online Protection" and "EOP" in content everywhere.

Version Updated:

  • No

Testing Completed:

  • None required; just documentation link updates

Checked that the validations are passing and have addressed any issues that are present:

  • n/a

@chrisda chrisda requested review from a team as code owners December 19, 2025 01:09
@chrisda
Copy link
Author

chrisda commented Dec 19, 2025

#sign-off

@v-atulyadav v-atulyadav added the Solution Solution specialty review needed label Dec 19, 2025
@v-shukore
Copy link
Contributor

v-shukore commented Dec 22, 2025

Hi @chrisda, since you have updated the workbook, you'll also need to repackage the solution. You've only updated the maintemplate, but the zip package needs to be updated as well. Please repackage the solution using the V3 tool and commit the changes. Thanks!

@v-shukore
Copy link
Contributor

v-shukore commented Jan 7, 2026

Hi @chrisda, any update on the above comment. Thanks!!

@chrisda
Copy link
Author

chrisda commented Jan 7, 2026

@v-shukore, I sent you an email with a question.

@v-shukore
Copy link
Contributor

v-shukore commented Jan 12, 2026

Hi @chrisda,
I checked my inbox but didn’t receive an email from your side. Could you please resend it?
Alternatively, if you have any questions or feedback, feel free to add them directly as comments on this GitHub PR.
Thanks!

@chrisda
Copy link
Author

chrisda commented Jan 12, 2026

@v-shukore, I resent my message from Jan 6, but I'll also respond here.

Hi @chrisda, since you have updated the workbook, you'll also need to repackage the solution. You've only updated the maintemplate, but the zip package needs to be updated as well. Please repackage the solution using the V3 tool and commit the changes. Thanks!

That statement doesn't mean anything to me. I have no idea what you're talking about. I was going through "content" looking for EOP references to replace. Are there instructions somewhere to do what you're asking?

@v-shukore
Copy link
Contributor

v-shukore commented Jan 14, 2026

Hi @chrisda,
Please package the solution using the V3 tool. You can follow the steps outlined in the README linked below to complete the packaging:
https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Create-Azure-Sentinel-Solution/V3/README.md

@chrisda
Copy link
Author

chrisda commented Jan 16, 2026 •
edited
Loading

@v-shukore, I followed the instructions (which are a bit wrong as the ARM Tools extension is apparently deprecated and replaced by the Bicep extension, and the instructions seem to be more about creating a package from scratch rather than updating).

I modified the SolutionMetadata.json files in both affected folders to add a lastPublishDate value. I ran the script, and this is what I got:

PS C:\GitHub\Azure-Sentinel> ./Tools/Create-Azure-Sentinel-Solution/V3/createSolutionV3.ps1
=======Starting Package Creation using V3 tool=========
Enter solution data folder path : NISTSP80053
Path NISTSP80053, DefaultPackageVersion is 3.0.0
Please provide data folder path from Solutions folder!

PS C:\GitHub\Azure-Sentinel> ./Tools/Create-Azure-Sentinel-Solution/V3/createSolutionV3.ps1
=======Starting Package Creation using V3 tool=========
Enter solution data folder path : ZeroTrust(TIC3.0)
Path ZeroTrust(TIC3.0), DefaultPackageVersion is 3.0.0
Please provide data folder path from Solutions folder!
PS C:\GitHub\Azure-Sentinel>

So, what do I do now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@v-shukore v-shukore

Labels

Solution Solution specialty review needed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@chrisda @v-shukore @v-atulyadav